fix(dsh): support alpha.1 session persistence drift - #134
Merged
Conversation
DeepSeek Harness 0.1.2-alpha.1 keeps session format 0 but adds range-encoded source provenance and three required persisted control events. Decode the exact native persistence contract at the DSH storage seam while preserving rc.2 scalar behavior and fail-closed validation. Regression coverage locks delivery relationships, duplicate model routes, and raw, zstd, and packed persistence. Implements Issue QoderAI#130 using docs/specs/2026-08-30-130-dsh-alpha1-session-compatibility.md. Validated with Node 22 and Node 24 focused DSH suites, npm test, Harness generated and package tests, package verification, and doc-link checks. Co-authored-by: Codex (GPT 5.6 Sol) <codex@openai.com>
phodal
added a commit
that referenced
this pull request
Aug 31, 2026
Align the root npm package, lockfile, public host manifests, compatibility note, and changelog on 0.6.6. This release collects the already-merged Studio internationalization and hosted-artifact work, Inspector evidence clarity, and DeepSeek Harness alpha.1 compatibility while leaving separately versioned Harness workspaces unchanged. The shipped behavior is backed by docs/specs/2026-08-28-studio-i18n.md, docs/specs/2026-08-29-agentic-json-canvas-intents.md, docs/specs/2026-08-31-inspector-usage-report-clarity.md, and the #134 compatibility spec. Validated with npm run check (1619 root tests, 173 Harness tests, 31 Harness UI tests, and 512 Studio tests), generated-source verification, pack verification (628 npm entries and 890 runtime ZIP entries), and a successful npm publish dry-run for @qoder-ai/better-harness@0.6.6. Co-authored-by: Codex (GPT 5.6 Sol) <codex@openai.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Keep Better Harness Session analysis compatible with the persisted Session
contract introduced by DeepSeek Harness
0.1.2-alpha.1.The DSH adapter now validates and expands native range-encoded
sourceEventSeqsand exactly recognizes the three new required persistedcontrol events without weakening rc.2 compatibility or fail-closed validation.
Why
Sessions are no longer rejected solely because of the new persistence
encoding or required control-event vocabulary.
Traceability and Scope
docs/specs/2026-08-30-130-dsh-alpha1-session-compatibility.mdscripts/session-analysis/platforms/dsh.mjstest/sessions/session-analysis-dsh-discovery.test.mjsProfile/Preset/Cordis runtime resolution, Skill or Instruction changes,
report semantics, installation changes, dependency changes, capability
flags, and promotion of alpha.1 to the qualified DSH baseline.
Change Type
Test and Review Evidence
npm testnpm run harness:generatednpm run harness:testnpm run pack:verifygit diff --check/ staged diff reviewManual or visual evidence:
No visual surface changed. Compatibility qualification used native DSH
0.1.2-alpha.1Session persistence artifacts for raw, zstd, packed provenance,and the three new required event types. The pre-fix baseline rejected those
contracts; the final adapter accepts valid native shapes while malformed known
events and unknown required events remain fail-closed.
Risk and Recovery
rc.2 scalar provenance remains supported; alpha.1 range provenance is decoded
only at the DSH physical-storage boundary. Local post-rebase validation covers
Node 22 and Node 24. Fresh PR CI is the authoritative Windows/Linux/macOS
cross-platform receipt.
No dependency, package, capability, report-schema, or DSH baseline change.
The patch only extends the existing format-0 DSH Session persistence adapter.
Revert this single compatibility commit to restore the prior rc.2-only
adapter behavior.
DSH
0.1.2-alpha.1remains a prerelease/source compatibility target ratherthan the qualified baseline. Do not claim npm-installable alpha support.
CHANGELOG note:
No CHANGELOG entry was added because this does not promote alpha.1 to the
qualified support baseline, and root
AGENTS.mdrestricts task-externalrelease metadata without explicit Issue/Spec authorization.
AI Involvement
Cobb04 defined and approved the compatibility boundary, reviewed the
qualification and independent pre-PR findings, required fail-closed regression
coverage, and authorized submission after maintainer Issue review. Codex
assisted with implementation, tests, traceability, and delivery validation.
Checklist
AGENTS.md,CONTRIBUTING.md, and the relevant canonical-owner guidance.CHANGELOG.md.